No matter how vast your C experience, no matter how advanced your C expertise, being a good C programmer does not make you a good C++ programmer. C programmers must learn to use the '++' part of 'C++', or the results will be lackluster. People who want the 'promise' of OOP, but who fail to put the 'OO' into OOP, are fooling themselves, and the balance sheet will show their folly.
C++ coding standards should be tempered by C++ experts. Asking comp.lang.c++ is a start (but don't use the term 'coding standard' in the question; instead simply say, 'what are the pros and cons of this technique?'). Seek out experts who can help guide you away from pitfalls. Get training. Buy libraries and see if 'good' libraries pass your coding standards. Do *not* set standards by yourself unless you have considerable experience in C++. Having no standard is better than having a bad standard, since improper 'official' positions 'harden' bad brain traces. There is a thriving market for both C++ training and libraries from which to pool expertise.
One more thing: any time demand for something is high, the potential for charlatans increases. Look before you leap. Also ask for student-reviews from past companies, since not even expertise makes someone a good communicator. Finally, select a practitioner who can teach, not a full time teacher who has a passing knowledge of the language/paradigm.
